Repository navigation
NG1: the Angular app on Workers - #2
Merged
Merged
Conversation
Vercel's Angular example (vercel/examples framework-boilerplates/angular at de86723: the Angular CLI 15's welcome app) in apps/web, moved to Angular 22.2. Angular 15 does not build on Node 22 (CLI 15 reports it unsupported, and TypeScript 4.8 fails on today's @types/node), so the build is Angular's esbuild application builder writing dist/browser, and the specs run on Angular's Vitest builder in jsdom instead of Karma and Chrome. AppComponent is standalone (bootstrapApplication with zone change detection and the router, routes still none) because Angular 22's test builder cannot compile an NgModule-declared component's template (reproduced on a stock ng new --standalone=false project); the welcome page's HTML and CSS are the template's byte for byte. The app's name is one seam (src/app/site.ts SITE_NAME = "angular-test", the template's title) that the banner reads. wrangler.jsonc serves dist/browser as Workers Static Assets with single-page-application routing, and worker/index.ts answers what the assets leave: a 404 for a path that names a file, the app for any other page. component.yaml is the deploy contract, with a smoke over the shell, the main bundle carrying the welcome page, a deep link and a missing file. Specs: the template's three, and one for the Next Steps terminal; tests/web (vitest): the seam, the build and test config, the Worker's routing and the template's page. The README's How it maps to Vercel records every swap. Co-Authored-By: Claude <noreply@anthropic.com> Orun-Task: NG-2
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Vercel's Angular example (vercel/examples framework-boilerplates/angular at de86723: the Angular CLI 15's welcome app) in apps/web, moved to Angular 22.2. Angular 15 does not build on Node 22 (CLI 15 reports it unsupported, and TypeScript 4.8 fails on today's @types/node), so the build is Angular's esbuild application builder writing dist/browser, and the specs run on Angular's Vitest builder in jsdom instead of Karma and Chrome. AppComponent is standalone (bootstrapApplication with zone change detection and the router, routes still none) because Angular 22's test builder cannot compile an NgModule-declared component's template (reproduced on a stock ng new --standalone=false project); the welcome page's HTML and CSS are the template's byte for byte. The app's name is one seam (src/app/site.ts SITE_NAME = "angular-test", the template's title) that the banner reads. wrangler.jsonc serves dist/browser as Workers Static Assets with single-page-application routing, and worker/index.ts answers what the assets leave: a 404 for a path that names a file, the app for any other page. component.yaml is the deploy contract, with a smoke over the shell, the main bundle carrying the welcome page, a deep link and a missing file. Specs: the template's three, and one for the Next Steps terminal; tests/web (vitest): the seam, the build and test config, the Worker's routing and the template's page. The README's How it maps to Vercel records every swap.
🤖 Generated with Claude Code